Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add OpUMod #781

Merged
merged 1 commit into from
Nov 16, 2024
Merged

Add OpUMod #781

merged 1 commit into from
Nov 16, 2024

Conversation

natgavrilenko
Copy link
Collaborator

No description provided.

@@ -59,7 +59,7 @@ public Event visitOpSelect(SpirvParser.OpSelectContext ctx) {
"expected two operands type '%s but received '%s' and '%s'",
id, type, op1.getType(), op2.getType());
}
if (op1.getType() instanceof IntegerType) {
if (op1.getType() instanceof IntegerType || op1.getType() instanceof BooleanType) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be not really related to the support for OpUMod and more of a "general fix". Am I right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. I need both for the empirical tests, and didn't want to create a separate commit just for this boolean.

@hernanponcedeleon hernanponcedeleon merged commit e678279 into development Nov 16, 2024
1 check passed
@hernanponcedeleon hernanponcedeleon deleted the op-mod branch November 16, 2024 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants